This page is a work in progress and the information found here is subject change.
RHQ Web Services is your standard WS*/XML/SOAP WSDL interface that exposes access to many of the RHQ server side objects in a platform independent manner. See Web Services Design for more details on which objects are exposed in the interface.
RHQ leverages JBossWS and JAXB to generate a WSDL for the RHQ implementation. Out of the box Web Services is NOT enabled.
To enable:
Shut down the RHQ Server in which you want to enable the Web Services
Navigate to <server-install-dir>/jbossas/server/default/deploy and rename jbossws.sar.rej to jbossws.sar (i.e. remove the ".rej" extension).
Restart the RHQ Server
Verify that your interface is up by browsing to https://localhost:7443/jbossws/services where "localhost" is the host of your RHQ Server and "7443" is the SSL port your server is listening to.
Initially we were going to generate 1 WSDL for each Stateless Session Bean that helped to group functionality. Due to performance reasons of such an approach we now generate one wsdl(WebservicesManagerBean.wsdl). The Web Service Deisgn link referenced has more details on which methods are exposed for which Stateless Session Beans.
At this point, you are ready to break out your favorite WSDL consumption toolkit to begin using the Web Service interface. We leverage JBossWs for the RHQ Web Services implementation so the following tools are included with the release to quickly enable consumption by java clients.
Within the <server-install-dir>/jbossas/bin directory you can use:
JBossWS wsconsume scripts to quickly generate java types for communication with the endpoint.
the wsrunclient script provided to setup the correct JBossWs/JAXB classpath to launching your application once you've written the desired procedures.